Augmented reality card activation experience

ABSTRACT

Various embodiments are generally directed to enhancing a card activation experience for an authorized card user when activating a new card by at least displaying various types of information related to the new card in augmented reality (AR) and allowing the user to perform the activation itself or experience other aspects of the activation process in AR. Information pertaining the successful activation of the card may also be provided to the user in AR.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/872,572, entitled “AUGMENTED REALITY CARD ACTIVATION EXPERIENCE”filed on May 12, 2020. The contents of the aforementioned applicationare incorporated herein by reference in its entirety.

BACKGROUND

When a new card (e.g., debit card, credit card, etc.) arrives in themail, an authorized user is required to activate the card in order touse it. There are various forms of activation. For example, the user canactivate the card by calling a telephone number indicated on a stickeradhered to the card, performing various authentication steps, andspeaking with a live or automated agent. In another example, the usercan activate the card by opening up a web browser, logging in the user'sonline account, performing various authentication steps, and pressing anactivation icon. In either example, the activation experience can beuninformative and dull.

SUMMARY

Various embodiments are generally directed to enhancing a cardactivation experience for an authorized card user when activating a newcard by at least displaying various types of information related to thenew card in augmented reality (AR) and allowing the user to perform theactivation itself or experience other aspects of the activation processin AR. Information pertaining the successful activation of the card mayalso be provided to the user in AR.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example data transmission system in accordancewith one or more embodiments.

FIG. 1B illustrates an example sequence diagram for providingauthenticated access in accordance with one or more embodiments.

FIG. 2 illustrates an example system using a contactless card inaccordance with one or more embodiments.

FIG. 3A illustrates an example contactless card in accordance with oneor more embodiments.

FIG. 3B illustrates an example contact pad of a contactless card inaccordance with one or more embodiments.

FIG. 4 illustrate example URL readings in accordance with one or moreembodiments.

FIG. 5 illustrates an example interface flow for downloading a bankingapp, user registration, and card activation initiation in accordancewith one or more embodiments.

FIG. 6 illustrates a first example of card information displayed inaugmented reality (AR) in accordance with one or more embodiments.

FIG. 7 illustrates a second example of card information displayed in ARin accordance with one or more embodiments.

FIG. 8 illustrate example card activation actions in accordance with oneor more embodiments.

FIG. 9 illustrates an example flow diagram in accordance with one ormore embodiments.

DETAILED DESCRIPTION

Various embodiments are generally directed to enhancing the cardactivation experience for an authorized card user by at least displayingvarious types of information related to the new card in augmentedreality (AR) and allowing the user to perform the activation orexperience various aspects of the activation process in AR.

In embodiments, during the activation experience, various informationand selectable options related to the card may be displayed in AR. Forinstance, if the card is a credit card, information such as the annualpercentage rate (APR) of the card, credit limit, payment due date, orthe like may be displayed around or adjacent to the card in AR. Othertypes of information may also be displayed in AR, such as informationassociated with one or more different types of components (e.g.,hardware, software, etc.) contained in the card or various graphics(e.g., contactless graphic) depicted on the card. In another instance,selectable options related to the card such as adding or removingauthorized users or setting up auto payment may also be displayed in AR.Moreover, instructions related to the activation process may bedisplayed and experienced in AR. It may be understood that, in AR, theinformation and selectable options may remain in predefined displaypositions relative to the card even if the physical position of thecamera changes.

In embodiments, upon an authorized card user (e.g., banking customer)receiving a new card (e.g., credit card, debit card, business card), theuser may tap the card to the user's mobile device (e.g., smartphone).When the card is tapped to the mobile device, the mobile device may reada uniform resource locator (URL) from the card via near fieldcommunication (NFC). In examples, the URL may direct the user to adownload location for downloading a banking application (otherwisereferred to herein as “banking app”) if the banking application is notalready on the mobile device. If the user already has the banking app onthe mobile device, the banking app may be launched instead. It may beunderstood that the term “tap” or “tapped” may broadly be referred to asbrining the card physically close to the mobile device such that the NFCreader coil of the mobile device can read or receive data from the card.

For example, the banking app may launch upon download and the user maybe guided through a registration process if the user is a new customer.Otherwise, existing customer may login to the banking app. As will befurther described below, existing customers may be able to login to thebanking app using “one-tap” authentication, which is a highly secure wayof verifying user identity to ensure, for example, that is the user whois actually logging in to the banking app and not a fraudster.

In embodiments, the card activation experience may begin in the bankingapp. For instance, the user may be instructed to point a camera of themobile device at the card. As described above, various types ofinformation related to the card and/or user selectable options may bedisplayed in AR. In a further instance, in AR, the border of the cardmay be outlined in a first color (e.g., red) to indicate that the cardhas not yet been activated. Instructions may also be provided to user inAR for completing the activation process. In one example, the user mayagain tap the card to the mobile device, which proceeds to activate thecard. When the card is placed back in front of the camera, the border ofthe card may be outlined in a second color different from the firstcolor (e.g., green) to indicate that the card has been activated. Inanother example, while in AR view, the user can physically tap the cardwith a finger, which completes the activation process. The border of thecard can again be outlined in a particular color.

In previous solutions, the card activation experience lacked excitementand was generally uninformative. The embodiments and examples describedherein overcome and are advantageous over the previous solutions in thata user can experience card activation in new, exciting, and informativeways. Allowing the user to interact with the card in AR during cardactivation engages the user in the process. Moreover, it is advantageousin allowing the user to change card-related options, such as theaddition or subtraction of authorized users or setting up auto payment,also enhances the activation experience.

Reference is now made to the drawings, where like reference numerals areused to refer to like elements throughout. In the following description,for the purpose of explanation, numerous specific details are set forthin order to provide a thorough understanding thereof. It may be evident,however, that the novel embodiments can be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form to facilitate a description thereof. Theintention is to cover all modification, equivalents, and alternativeswithin the scope of the claims.

FIG. 1A illustrates an example data transmission system according to oneor more embodiments. As further discussed below, system 100 may includecontactless card 105, client device 110, network 115, and server 120.Although FIG. 1A illustrates single instances of the components, system100 may include any number of components.

System 100 may include one or more contactless cards 105, which arefurther explained below with reference to FIG. 3A and FIG. 3B. In someembodiments, contactless card 105 may be in wireless communication,utilizing NFC in an example, with client device 110.

System 100 may include client device 110, which may be a network-enabledcomputer. As referred to herein, a network-enabled computer may include,but is not limited to a computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer, aworkstation, a phone, a smartphone, a handheld PC, a personal digitalassistant, a thin client, a fat client, an Internet browser, or otherdevice. Client device 110 also may be a mobile computing device, forexample, an iPhone, iPod, iPad from Apple® or any other suitable devicerunning Apple's iOS® operating system, any device running Microsoft'sWindows® Mobile operating system, any device running Google's Android®operating system, and/or any other suitable mobile computing device,such as a smartphone, a tablet, or like wearable mobile device.

The client device 110 device can include a processor and a memory, andit is understood that the processing circuitry may contain additionalcomponents, including processors, memories, error and parity/CRCcheckers, data encoders, anti-collision algorithms, controllers, commanddecoders, security primitives and tamper-proofing hardware, as necessaryto perform the functions described herein. The client device 110 mayfurther include a display and input devices. The display may be any typeof device for presenting visual information such as a computer monitor,a flat panel display, and a mobile device screen, including liquidcrystal displays, light-emitting diode displays, plasma panels, andcathode ray tube displays. The input devices may include any device forentering information into the user's device that is available andsupported by the user's device, such as a touch-screen, keyboard, mouse,cursor-control device, touch-screen, microphone, digital camera, videorecorder or camcorder. These devices may be used to enter informationand interact with the software and other devices described herein.

In some examples, client device 110 of system 100 may execute one ormore applications, such as software applications, that enable, forexample, network communications with one or more components of system100 and transmit and/or receive data.

Client device 110 may be in communication with one or more servers 120via one or more networks 115 and may operate as a respective front-endto back-end pair with server 120. Client device 110 may transmit, forexample from a mobile device application executing on client device 110,one or more requests to server 120. The one or more requests may beassociated with retrieving data from server 120. Server 120 may receivethe one or more requests from client device 110. Based on the one ormore requests from client device 110, server 120 may be configured toretrieve the requested data from one or more databases (not shown).Based on receipt of the requested data from the one or more databases,server 120 may be configured to transmit the received data to clientdevice 110, the received data being responsive to one or more requests.

System 100 may include one or more networks 115. In some examples,network 115 may be one or more of a wireless network, a wired network orany combination of wireless network and wired network and may beconfigured to connect client device 110 to server 120. For example,network 115 may include one or more of a fiber optics network, a passiveoptical network, a cable network, an Internet network, a satellitenetwork, a wireless local area network (LAN), a Global System for MobileCommunication, a Personal Communication Service, a Personal AreaNetwork, Wireless Application Protocol, Multimedia Messaging Service,Enhanced Messaging Service, Short Message Service, Time DivisionMultiplexing based systems, Code Division Multiple Access based systems,D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and802.11g, Bluetooth, NFC, Radio Frequency Identification (RFID), Wi-Fi,and/or the like.

In addition, network 115 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 802.3, a wide area network, awireless personal area network, a LAN, or a global network such as theInternet. In addition, network 115 may support an Internet network, awireless communication network, a cellular network, or the like, or anycombination thereof. Network 115 may further include one network, or anynumber of the exemplary types of networks mentioned above, operating asa stand-alone network or in cooperation with each other. Network 115 mayutilize one or more protocols of one or more network elements to whichthey are communicatively coupled. Network 115 may translate to or fromother protocols to one or more protocols of network devices. Althoughnetwork 115 is depicted as a single network, it should be appreciatedthat according to one or more examples, network 115 may include aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, such as credit card association networks, and homenetworks.

System 100 may include one or more servers 120. In some examples, server120 may include one or more processors, which are coupled to memory.Server 120 may be configured as a central system, server or platform tocontrol and call various data at different times to execute a pluralityof workflow actions. Server 120 may be configured to connect to the oneor more databases. Server 120 may be connected to at least one clientdevice 110.

FIG. 1B illustrates an example sequence diagram for providingauthenticated access according to one or more embodiments. The diagrammay include contactless card 105 and client device 110, which mayinclude an application 122 and processor 124. FIG. 1B may referencesimilar components as illustrated in FIG. 1A.

At step 102, the application 122 communicates with the contactless card105 (e.g., after being brought near the contactless card 105).Communication between the application 122 and the contactless card 105may involve the contactless card 105 being sufficiently close to a cardreader (not shown) of the client device 110 to enable NFC data transferbetween the application 122 and the contactless card 105.

At step 104, after communication has been established between clientdevice 110 and contactless card 105, the contactless card 105 generatesa message authentication code (MAC) cryptogram. In some examples, thismay occur when the contactless card 105 is read by the application 122.In particular, this may occur upon a read, such as an NFC read, of anear field data exchange (NDEF) tag, which may be created in accordancewith the NFC Data Exchange Format.

For example, a reader, such as application 122, may transmit a message,such as an applet select message, with the applet ID of an NDEFproducing applet. Upon confirmation of the selection, a sequence ofselect file messages followed by read file messages may be transmitted.For example, the sequence may include “Select Capabilities file,” “ReadCapabilities file,” and “Select NDEF file.” At this point, a countervalue maintained by the contactless card 105 may be updated orincremented, which may be followed by “Read NDEF file.” At this point,the message may be generated which may include a header and a sharedsecret. Session keys may then be generated. The MAC cryptogram may becreated from the message, which may include the header and the sharedsecret. The MAC cryptogram may then be concatenated with one or moreblocks of random data, and the MAC cryptogram and a random number (RND)may be encrypted with the session key. Thereafter, the cryptogram andthe header may be concatenated, and encoded as ASCII hex and returned inNDEF message format (responsive to the “Read NDEF file” message).

In some examples, the MAC cryptogram may be transmitted as an NDEF tag,and in other examples the MAC cryptogram may be included with a uniformresource indicator (e.g., as a formatted string).

In some examples, application 122 may be configured to transmit arequest to contactless card 105, the request comprising an instructionto generate a MAC cryptogram.

At step 106, the contactless card 105 sends the MAC cryptogram to theapplication 122. In some examples, the transmission of the MACcryptogram occurs via NFC, however, the present disclosure is notlimited thereto. In other examples, this communication may occur viaBluetooth, Wi-Fi, or other means of wireless data communication.

At step 108, the application 122 communicates the MAC cryptogram to theprocessor 124. At step 112, the processor 124 verifies the MACcryptogram pursuant to an instruction from the application 122. Forexample, the MAC cryptogram may be verified, as explained below.

In some examples, verifying the MAC cryptogram may be performed by adevice other than client device 110, such as a server 120 in datacommunication with the client device 110 (as shown in FIG. 1A). Forexample, processor 124 may output the MAC cryptogram for transmission toserver 120, which may verify the MAC cryptogram.

In some examples, the MAC cryptogram may function as a digital signaturefor purposes of verification. Other digital signature algorithms, suchas public key asymmetric algorithms, e.g., the Digital SignatureAlgorithm and the RSA algorithm, or zero knowledge protocols, may beused to perform this verification.

It may be understood that in some examples, the contactless card 105 mayinitiate communication after the contactless card is brought near theclient device 110. By way of example, the contactless card 105 may sendthe client device 110 a message, for instance, indicating that thecontactless card has established communication. Thereafter, theapplication 122 of client device 110 may proceed to communicate with thecontactless card at step 102, as described above.

FIG. 2 illustrates an example system 200 using a contactless card.System 200 may include a contactless card 205, one or more clientdevices 210, network 215, servers 220, 225, one or more hardwaresecurity modules 230, and a database 235. Although FIG. 2 illustratessingle instances of the components, system 200 may include any number ofcomponents.

System 200 may include one or more contactless cards 205, which arefurther explained below with respect to FIG. 3A and FIG. 3B. In someexamples, contactless card 205 may be in wireless communication, forexample NFC communication, with client device 210. For example,contactless card 205 may include one or more chips, such as a radiofrequency identification chip, configured to communication via NFC orother short-range protocols. In other embodiments, contactless card 205may communicate with client device 210 through other means including,but not limited to, Bluetooth, satellite, Wi-Fi, wired communications,and/or any combination of wireless and wired connections. According tosome embodiments, contactless card 205 may be configured to communicatewith card reader 213 (which may otherwise be referred to herein as NFCreader, NFC card reader, or reader) of client device 210 through NFCwhen contactless card 205 is within range of card reader 213. In otherexamples, communications with contactless card 205 may be accomplishedthrough a physical interface, e.g., a universal serial bus interface ora card swipe interface.

System 200 may include client device 210, which may be a network-enabledcomputer. As referred to herein, a network-enabled computer may include,but is not limited to: e.g., a computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer, aworkstation, a mobile device, a phone, a handheld PC, a personal digitalassistant, a thin client, a fat client, an Internet browser, or otherdevice. One or more client devices 210 also may be a mobile device; forexample, a mobile device may include an iPhone, iPod, iPad from Apple®or any other mobile device running Apple's iOS® operating system, anydevice running Microsoft's Windows® Mobile operating system, any devicerunning Google's Android® operating system, and/or any other smartphoneor like wearable mobile device. In some examples, the client device 210may be the same as, or similar to, a client device 110 as described withreference to FIG. 1A or FIG. 1B.

Client device 210 may be in communication with one or more servers 220and 225 via one or more networks 215. Client device 210 may transmit,for example from an application 211 executing on client device 210, oneor more requests to one or more servers 220 and 225. The one or morerequests may be associated with retrieving data from one or more servers220 and 225. Servers 220 and 225 may receive the one or more requestsfrom client device 210. Based on the one or more requests from clientdevice 210, one or more servers 220 and 225 may be configured toretrieve the requested data from one or more databases 235. Based onreceipt of the requested data from the one or more databases 235, one ormore servers 220 and 225 may be configured to transmit the received datato client device 210, the received data being responsive to one or morerequests.

System 200 may include one or more hardware security modules (HSM) 230.For example, one or more HSMs 230 may be configured to perform one ormore cryptographic operations as disclosed herein. In some examples, oneor more HSMs 230 may be configured as special purpose security devicesthat are configured to perform the one or more cryptographic operations.The HSMs 230 may be configured such that keys are never revealed outsidethe HSM 230, and instead are maintained within the HSM 230. For example,one or more HSMs 230 may be configured to perform at least one of keyderivations, decryption, and MAC operations. The one or more HSMs 230may be contained within, or may be in data communication with, servers220 and 225.

System 200 may include one or more networks 215. In some examples,network 215 may be one or more of a wireless network, a wired network orany combination of wireless network and wired network, and may beconfigured to connect client device 210 to servers 220 and/or 225. Forexample, network 215 may include one or more of a fiber optics network,a passive optical network, a cable network, a cellular network, anInternet network, a satellite network, a wireless LAN, a Global Systemfor Mobile Communication, a Personal Communication Service, a PersonalArea Network, Wireless Application Protocol, Multimedia MessagingService, Enhanced Messaging Service, Short Message Service, TimeDivision Multiplexing based systems, Code Division Multiple Access basedsystems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1,802.11n and 802.11g, Bluetooth, NFC, RFID, Wi-Fi, and/or any combinationof networks thereof. As a non-limiting example, communications fromcontactless card 205 and client device 210 may include NFCcommunication, cellular network between client device 210 and a carrier,and Internet between the carrier and a back-end.

In addition, network 215 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 802.3, a wide area network, awireless personal area network, a local area network, or a globalnetwork such as the Internet. In addition, network 215 may support anInternet network, a wireless communication network, a cellular network,or the like, or any combination thereof. Network 215 may further includeone network, or any number of the exemplary types of networks mentionedabove, operating as a stand-alone network or in cooperation with eachother. Network 215 may utilize one or more protocols of one or morenetwork elements to which they are communicatively coupled. Network 215may translate to or from other protocols to one or more protocols ofnetwork devices. Although network 215 is depicted as a single network,it should be appreciated that according to one or more examples, network215 may include a plurality of interconnected networks, such as, forexample, the Internet, a service provider's network, a cable televisionnetwork, corporate networks, such as credit card association networks,and home networks.

In various examples according to the present disclosure, client device210 of system 200 may execute one or more applications 211, and includeone or more processors 212, and one or more card readers 213. Forexample, one or more applications 211, such as software applications,may be configured to enable, for example, network communications withone or more components of system 200 and transmit and/or receive data.It is understood that although only single instances of the componentsof client device 210 are illustrated in FIG. 2, any number of devices210 may be used. Card reader 213 may be configured to read from and/orcommunicate with contactless card 205. In conjunction with the one ormore applications 211, card reader 213 may communicate with contactlesscard 205. In examples, the card reader 213 may include circuitry orcircuitry components, e.g., NFC reader coil, that generates a magneticfield to allow communication between the client device 210 and thecontactless card 205.

The application 211 of any of client device 210 may communicate with thecontactless card 205 using short-range wireless communication (e.g.,NFC). The application 211 may be configured to interface with a cardreader 213 of client device 210 configured to communicate with acontactless card 205. As should be noted, those skilled in the art wouldunderstand that a distance of less than twenty centimeters is consistentwith NFC range.

In some embodiments, the application 211 communicates through anassociated reader (e.g., card reader 213) with the contactless card 205.

In some embodiments, card activation may occur without userauthentication. For example, a contactless card 205 may communicate withthe application 211 through the card reader 213 of the client device 210through NFC. The communication (e.g., a tap of the card proximate thecard reader 213 of the client device 210) allows the application 211 toread the data associated with the card and perform an activation. Insome cases, the tap may activate or launch application 211 and theninitiate one or more actions or communications with an account server225 to activate the card for subsequent use. In some cases, if theapplication 211 is not installed on client device 210, a tap of the cardagainst the card reader 213 may initiate a download of the application211 (e.g., navigation to an application download page). Subsequent toinstallation, a tap of the card may activate or launch the application211, and then initiate (e.g., via the application or other back-endcommunication) activation of the card. After activation, the card may beused in various transactions including commercial transactions.

According to some embodiments, the contactless card 205 may include avirtual payment card. In those embodiments, the application 211 mayretrieve information associated with the contactless card 205 byaccessing a digital wallet implemented on the client device 210, whereinthe digital wallet includes the virtual payment card. In some examples,virtual payment card data may include one or more static or dynamicallygenerated virtual card numbers.

Server 220 may include a web server in communication with database 235.Server 225 may include an account server. In some examples, server 220may be configured to validate one or more credentials from contactlesscard 205 and/or client device 210 by comparison with one or morecredentials in database 235. Server 225 may be configured to authorizeone or more requests, such as payment and transaction, from contactlesscard 205 and/or client device 210.

FIG. 3A illustrates one or more contactless cards 300, which may includea payment card, such as a credit card, debit card, or gift card, issuedby a service provider 305 displayed on the front or back of the card300. In some examples, the contactless card 300 is not related to apayment card, and may include, without limitation, an identificationcard. In some examples, the payment card may include a dual interfacecontactless payment card. The contactless card 300 may include asubstrate 310, which may include a single layer, or one or morelaminated layers composed of plastics, metals, and other materials.Exemplary substrate materials include polyvinyl chloride, polyvinylchloride acetate, acrylonitrile butadiene styrene, polycarbonate,polyesters, anodized titanium, palladium, gold, carbon, paper, andbiodegradable materials. In some examples, the contactless card 300 mayhave physical characteristics compliant with the ID-1 format of theISO/IEC 7810 standard, and the contactless card may otherwise becompliant with the ISO/IEC 14443 standard. However, it is understoodthat the contactless card 300 according to the present disclosure mayhave different characteristics, and the present disclosure does notrequire a contactless card to be implemented in a payment card.

The contactless card 300 may also include identification information 315displayed on the front and/or back of the card, and a contact pad 320.The contact pad 320 may be configured to establish contact with anothercommunication device, such as a user device, smart phone, laptop,desktop, or tablet computer. The contactless card 300 may also includeprocessing circuitry, antenna and other components not shown in FIG. 3A.These components may be located behind the contact pad 320 or elsewhereon the substrate 310. The contactless card 300 may also include amagnetic strip or tape, which may be located on the back of the card(not shown in FIG. 3A).

As illustrated in FIG. 3B, the contact pad 320 of FIG. 3A may includeprocessing circuitry 325 for storing and processing information,including a microprocessor 330 and a memory 335. It is understood thatthe processing circuitry 325 may contain additional components,including processors, memories, error and parity/CRC checkers, dataencoders, anti-collision algorithms, controllers, command decoders,security primitives and tamper-proofing hardware, as necessary toperform the functions described herein.

The memory 335 may be a read-only memory, write-once read-multiplememory or read/write memory, e.g., RAM, ROM, and EEPROM, and thecontactless card 300 may include one or more of these memories. Aread-only memory may be factory programmable as read-only or one-timeprogrammable. One-time programmability provides the opportunity to writeonce then read many times. A write once/read-multiple memory may beprogrammed at a point in time after the memory chip has left thefactory. Once the memory is programmed, it may not be rewritten, but itmay be read many times. A read/write memory may be programmed andre-programed many times after leaving the factory. It may also be readmany times.

The memory 335 may be configured to store one or more applets 340, oneor more counters 345, one or more diversified keys 347, one or morecustomer identifiers 350, and one or more uniform resource locators(URLs). The one or more applets 340 may include one or more softwareapplications configured to execute on one or more contactless cards,such as Java Card applet. However, it is understood that applets 340 arenot limited to Java Card applets, and instead may be any softwareapplication operable on contactless cards or other devices havinglimited memory. The one or more counters 345 may include a numericcounter sufficient to store an integer. As will be further describedbelow, the one or more diversified keys 347 may be used to encryptvarious information, such as information about the user or customer(e.g., customer identifier 450) to generate cryptogram(s) that can besent to, for example, a mobile device for at least authenticationpurposes. The customer identifier 350 may include a unique alphanumericidentifier assigned to a user of the contactless card 300, and theidentifier may distinguish the user of the contactless card from othercontactless card users. In some examples, the customer identifier 350may identify both a customer and an account assigned to that customerand may further identify the contactless card associated with thecustomer's account. The one or more URLs 355 may include uniqueaddresses associated with a World Wide Web page or the like, and in someinstance, may be generated by the processing circuitry 325 based on aURL generation event (e.g., the card 300 is tapped to a computingdevice).

The processor and memory elements of the foregoing exemplary embodimentsare described with reference to the contact pad, but the presentdisclosure is not limited thereto. It is understood that these elementsmay be implemented outside of the pad 320 or entirely separate from it,or as further elements in addition to processor 330 and memory 335elements located within the contact pad 320.

In some examples, the contactless card 300 may include one or moreantennas 355. The one or more antennas 355 may be placed within thecontactless card 300 and around the processing circuitry 325 of thecontact pad 320. For example, the one or more antennas 355 may beintegral with the processing circuitry 325 and the one or more antennas355 may be used with an external booster coil. As another example, theone or more antennas 355 may be external to the contact pad 320 and theprocessing circuitry 325.

In an embodiment, the coil of contactless card 300 may act as thesecondary of an air core transformer. The terminal may communicate withthe contactless card 300 by cutting power or amplitude modulation. Thecontactless card 300 may infer the data transmitted from the terminalusing the gaps in the contactless card's power connection, which may befunctionally maintained through one or more capacitors. The contactlesscard 300 may communicate back by switching a load on the contactlesscard's coil or load modulation. Load modulation may be detected in theterminal's coil through interference.

As explained above, the contactless cards 300 may be built on a softwareplatform operable on smart cards or other devices having limited memory,such as JavaCard, and one or more or more applications or applets may besecurely executed. Applets may be added to contactless cards to providea one-time password (OTP) for multifactor authentication (MFA) invarious mobile application-based use cases. Applets may be configured torespond to one or more requests, such as near field data exchangerequests, from a reader, such as a mobile NFC reader, and produce anNDEF message that includes a cryptographically secure OTP encoded as anNDEF text tag.

In examples, when preparing to send data (e.g., to a mobile device, to aserver, etc.), the contactless card 300 may increment a counter value ofa counter of the one or more counters 345. The contactless card 300 maythen provide a master key, which may be a distinct key stored on thecard 300, and the counter value as input to a cryptographic algorithm,which produces a diversified key as output, which may be one of thediversified keys 347. It is understood that the master key and thecounter value is also stored in memory of a device or componentreceiving data from the contactless card 300 so as to decrypt the datausing the diversified key that was used by the card to encrypt thetransmitted data. The cryptographic algorithm may include encryptionalgorithms, hash-based message authentication code (HMAC) algorithms,cipher-based message authentication code (CMAC) algorithms, and thelike. Non-limiting examples of the cryptographic algorithm may include asymmetric encryption algorithm such as 3DES or AES128; a symmetric HMACalgorithm, such as HMAC-SHA-256; and a symmetric CMAC algorithm such asAES-CMAC. The contactless card 300 may then encrypt the data (e.g., thecustomer identifier 350 and any other data) using the diversified key inthe form of one or more cryptograms that can be sent to a mobile device,for example, as NFC data exchange format (NDEF) messages. Thecontactless card 300 may then transmit the encrypted data (e.g.,cryptograms) to the mobile device, which can then decrypt thecryptograms using the diversified key (e.g., the diversified keygenerated by the mobile device using the counter value and the masterkey stored in memory thereof).

FIG. 4 illustrates example URL readings 400 and 460 according to one ormore embodiments. In one example, an authorized card user may receive anew card 402 (e.g., credit card, debit card, contactless card). To startthe activation experience, the user may be instructed to tap the card402 to the user's mobile device 404 (e.g., smartphone, tablet, anyportable computing device). In some examples, the instructions may bepresented to the user by way of a sticker adhered to the card 402. Itmay be understood that tapping the card 402 to the mobile device 404 maybroadly refer to the card being in sufficient or requisite proximity tothe mobile device 404 such that at least one near field communication(NFC) reader coil of the mobile device 404 is able to communicate (e.g.,read or receive data) with the card 402. As shown in URL reading 400,when the card 402 is tapped to or brought near the mobile device 404,the mobile device 404 can read or receive a URL from the card 402. Forinstance, the URL may be one or more of the URLs 355 stored in card 300,as described above with respect to FIG. 3B.

In another example, the authorized card user may receive the new card402 in an envelope 462 (e.g., in the mail). As illustrated in URLreading 460, the envelope 462 may include a sticker 464, or in someexamples, a Quick Response (QR) code 466 (as shown by the dashed lines).The sticker 464 or the QR code 466 may be placed or arranged inside ofthe envelope 462 for security purposes, which can be accessed by tearingor ripping the envelope 462 open. In other instance, the sticker 464 orQR code 466 may be provided on separate paper, which the authorized usercan pull out of the envelope 462.

The user may then be instructed to tap the mobile device 404 to thesticker 464 (or, vise verse, tap the sticker 464 to the mobile device404) to read or receive the URL. In embodiments, the sticker 464 may bean NFC-enabled sticker that provides the URL via NFC communication. Inother embodiments, the sticker may include a graphic that can be scannedby the mobile device 404 allowing the device 404 to obtain the URL. Forinstance, the graphic can be the URL itself, which the camera of themobile device 404 can be configured to read. The QR code 466 may providesimilar functionalities as the sticker 464, which can be read or scannedby the camera of the mobile device 404 to acquire the URL.

FIG. 5 illustrates an example interface flow 500 for downloading abanking app, user registration, and card activation initiation accordingto one or more embodiments. Upon reading or receiving a URL from thecard (or sticker or QR code), as described above with respect to FIG. 4,the URL directs or redirects the mobile computing device to a downloadlocation for downloading a banking app, which, for example, may be aWorld Wide Web page. As illustrated, the user may land on a downloadinterface 502 if the user does not already have the banking appinstalled on the mobile device. In examples, the download interface 502may include screen 504 that indicates the requisite banking app has notyet been downloaded to the mobile device and instructs the user todownload the banking app. To do so, the user may select or press theicon 506, which begins the download process.

After the banking app has been downloaded, the mobile device mayautomatically launch the app. As illustrated in screen 508, a bankingapp 510 may request that the user complete registration via the beginregistration icon 512. The registration process may involve the userproviding personal information or other types of user-relatedinformation involved in setting up a user account, such as creating ausername, password, and setting up one-tap authentication, which will befurther described below. Once the registration process has beencompleted by the user, the banking app 510 may instruct the user toinitiate the activation process. For example, screen 514 may ask theuser to point the camera of the mobile device at the card and press thebegin activation icon 516. In other examples, the user can select thebegin activation icon 516 first and then point the camera at the card.

In other embodiments, the banking app 510 may already be downloaded andinstalled on the mobile device. In that instance, the banking app may beautomatically opened and launched when the mobile device reads orreceives the URL from the card, as indicated by the dashed lines in FIG.5. As shown, the user may be instructed to login to the banking app 510via screen 520. To login, the user may perform one or more various typesof authentication. For example, the user may login by providing ausername and password. In another example, the user may perform one-tapauthentication to login.

According to embodiments, one-tap authentication may involve the userplacing, tapping, or bringing near a contactless card to a designatedarea of the user's mobile device. The user computing device may detectthe contactless card via near field communication (NFC) and receive oneor more cryptograms from the contactless card. Information contained inthe cryptogram(s), which may identify the true owner of the contactlesscard, may be compared or matched against authentication informationrelated to the user logging in to the banking app. If they match, asuccessful user identity verification can be confirmed. In someexamples, the contactless card used to perform the one-tapauthentication may be an already existing, active card belonging to theuser. In other examples, the new card—the card that is beingactivated—may be used to perform the one-tap authentication. It may beunderstood that a cryptogram may broadly refer to any encrypted text,data, or information. It may further be understood that the one or morecryptograms may be received as NFC data exchange format (NDEF) messages.

In examples, the one or more received cryptograms may containinformation at least identifying the user or other related informationindicating that the card belongs to a particular user. For instance, thecard-user information may be any type of data or information (e.g., IDnumber, customer number, etc.) associating the contactless card to theuser, which may be created or established when the contactless card iscreated for the user and/or at backend systems when the user signs up orapplies for the contactless card. Afterwards, the information containedin the one or more received cryptograms may be matched or comparedagainst authentication information associated with the user to verifythe identity of the user. The authentication information is any type ofdata or information identifying the user signed-in to the banking app(e.g., ID number, customer number, etc.).

In one example, the banking app 510 may receive the one or morecryptograms from the contactless card and send the cryptogram(s) to oneor more remote computing devices, which may be secure backend servers,to perform the decryption of the cryptograms and determine whether theinformation contained in the one or more cryptograms matchauthentication information related to the user. The one or more remotecomputing devices may then send to the banking app 510 an indication orconfirmation of verification of the user's identity. In at least thatregard, most (if not all) of the identity verification process may beperformed at one or more secure and remote computing devices, which maybe advantageous in certain applications or use cases.

In another example, the banking app 510 may be configured to decrypt theone or more cryptograms received from the contactless card using atleast one key (e.g., a private key, a decryption key, a keycorresponding to a specific encryption-decryption scheme). The bankingapp 510 may securely access or receive authentication informationrelated to the user from one or more remote computing devices, such asbackend servers. The authentication information may contain at least anidentifier or any information indicating the identity of the user loggedinto the banking app 510. The banking app 510 may then determine whetherthe received authentication information and the decrypted cryptograminformation received from the contactless card match to verify that thecontactless card actually belongs to the user and/or to verify that theuser is actually the user claims to be.

Upon successful verification and authentication of the user's identity,the banking app 510 may display an indication that the user hassuccessfully logged in. Thereafter, the user may continue with the cardactivation experience within the banking app 510, as will be furtherdescribed below.

FIG. 6 illustrates card information 600 displayed in augmented reality(AR) according to one or more embodiments. When the customer card 402(e.g., front-side forward) is placed in front of the camera of theuser's mobile device, the banking app 510 may display various types ofcard information in AR during the activation experience.

As shown, card information 600 may include an annual percentage rate(APR) associated with the customer card 402 and may be displayed in ARadjacent to the card. For example, the APR may be eighteen percent. Asfurther shown, a line or any suitable indicator may virtually connectthe APR information to the card. The line or indicator may be any color,size, thickness, shape, etc. that allows the information to be easilyread or deciphered by the user. Moreover, credit limit information maybe displayed in AR (e.g., $25,000) adjacent to the card 402. Further,payment due date information may also be displayed adjacent to the card.As shown, for instance, a minimum payment may be due every fifth of eachmonth.

In further embodiments, user selectable options associated with thecustomer card may also be displayed adjacent to the card in AR. The userselectable options may be related to, for instance, adding orsubtracting authorized card users or setting up or modifying autopay. Asillustrated, the user may be able to interact with the “change” icondisplayed in AR under the “authorized users” AR component. In responseto touching, pressing, or otherwise selecting the change icon, the usermay be able to add, subtract, or modify authorized users of the customercard 402. Similarly, the user may select or press the “change” iconunder the “setup autopay” AR component. In response, the user may beable to enroll or disenroll in autopay or modify features associatedtherewith.

In yet further embodiments, other types of information, such asinformation related to components graphically depicted or physicallyindicated on the customer card 402 itself, may be displayed adjacent tothe card in AR. As shown, information related to the embedded microchipmay be displayed (e.g., “chip enabled” or “NFC enabled”). If thecustomer is a new customer, words of appreciation can be displayed nextto the customer's name (e.g., “you're new! Thank you for banking withus!”). In other examples, next to the electronic funds transfer companygraphic (e.g., company facilitating the exchange of funds associatedwith the card transactions), the user may select the “view” icon underthe “see merchants that support this card” AR component to viewinformation regarding the respective merchants or businesses thatsupport the customer card 402.

In examples, a border or outline of the customer card 402 can be colorcoded in AR to indicate activation-related information. For instance,the border 604 customer card 402 may be outlined in red to indicate thatthe card 402 has not yet been activated and thus cannot be used atmerchants. As will be further described below, upon completing theactivation process, the border 604 of the card 402 may be outlined ingreen to indicate that the user has successfully activated the card.

As further illustrated, at least two activation instructions may bedisplayed in AR underneath the customer card 402, both of which will befurther explained below with respect to at least FIG. 8. In one example,the user may be instructed to tap the card 402 to the mobile device tocomplete the activation experience. In another example, the user may beinstructed to physically tap the card with the user's finger to completethe activation experience.

Since the user may view the card information 600 in AR from differentangles and at different positions, it may be understood that the bankingapp 510 may be configured to perform automatic scaling or scale-to-fitprocedures such that the card information 600 remain displayed in theirrespective and correct positions relative to the customer card 402regardless of the differing viewing angles or positions.

FIG. 7 illustrates card information 700 displayed in augmented reality(AR) according to one or more embodiments. As shown, the backside of thecustomer card 402 may be placed in front of the camera of the user'smobile device during the activation experience, which causes the bankingapp 510 to display card information 700 in AR.

Similar to the card information 600, described above, card information700 may also include various types of information about differentcomponents (graphical or otherwise) arranged, depicted, or illustratedon the back of the card 402. For example, information related to thegraphic or symbol indicating that the customer card 402 is contactlessmay be virtually displayed adjacent to the card and read “Your card iscontactless, which means you can simply tap the card to pay or performother actions.” In a further example, information related to themagnetic stripe may displayed in AR adjacent to the stripe and state“You can swipe your card the old-fashioned way.”

Moreover, reminder information may be displayed in AR, such as “Don'tforget to sign your card after you activate” adjacent to the signatureline. In yet another example, various facts can be displayed, such as“Fun Fact: We have over 700 branches and numerous café locations”adjacent to the card issuer graphic on the back of the customer card402. And similar to the border 604 described above, a border 704 may bedisplayed around the card 402 and may be color-coded (e.g., red) toindicate that the card still has not yet been activated.

In examples, the card activation experience may be advantageouslyenhanced by the banking app 510 seamlessly transitioning AR display frominformation 600 to information 700 as the user flips the customer card402 from the front-side to the backside, and transitioning AR displayfrom information 700 to information 600 as the user flips the card 402from the backside to the front-side. In at least that regard, the usermay be able to enjoy a wholly interactive card activation experience inaugmented reality with the physical card itself.

FIG. 8 illustrate example card activation actions 800 according to oneor more embodiments. At least two different activation actions areshown: tapping the customer card 402 to the mobile device 404 andtapping the card 402 itself with the user's finger.

After the user has experienced the display of the card information 600and 700 in AR, the user may wish to complete the activation experienceand officially activate the card. In one example, the user may tap thecustomer card 402 to the mobile device 404, which the banking app 510may detect, to activate the card. Upon detecting that the card 402 hasbeen tapped, the mobile device 404 via the banking app 510 maycommunicate with one or more backend servers to signal that a cardactivation action has been performed and to confirm official activationof the card so that the customer card 404 is active and ready for use.After tapping the card to the phone, the user may place the card 402back in front of the camera of the mobile device 404. As shown, a border802 around the card 402 may now be color-coded, e.g., in green, toindicate that the card has been successfully activated.

In another example, the user may tap the customer card 402 with theuser's finger in front of the camera of the mobile device 404. Similarto the card tapping action, this finger tapping action may cause thebanking app 510 to communicate with the one or more backend servers tocomplete the activation process. As further illustrated, a border 804around the card 402 may also be color-coded, e.g., in green, to indicatethat the card has been successfully activated and ready for use.

FIG. 9 illustrates an example flow diagram 900 according to one or moreembodiments. The flow diagram 900 is related to enhancing a cardactivation experience by displaying various types of card information inaugmented reality. It may be understood that the blocks of the flowdiagram 900 and the features described therein are not required to beperformed in any particular order. Moreover, it may be understood thatthe flow diagram 900 and the features described therein may be executedby one or more processors.

At block 902, a plurality of images of a customer card may be receivedby a camera of, e.g., a mobile computing device. The customer card maybe a new card associated with an authorized user that requiresactivation and may be placed in front of the camera. The images may beprocessed by a banking app, which may be downloaded and installed (ifnot already downloaded and installed on the mobile device) via a URLreading, as described above.

At block 904, information related to the customer card may be displayedin augmented reality (AR). In examples, information such as the creditlimit, annual percentage rate, and due date of monthly minimum paymentsmay be displayed adjacent to the card. In further examples, informationrelated to selectable options associated with the card, such as addingor subtracting authorized users and setting up autopay may be displayed.The user may select an AR icon to change these options, as describedabove. Moreover, information related to various components arranged onor graphically or textually depicted on the card may be displayed. Forexample, “chip enabled” may be displayed in AR adjacent to the cardchip. Other types of information, such as a statement thanking thecustomer for being a customer can be displayed next to the customer'sname on the card. Card information for both the front and back of thecard may be displayed in AR.

At block 906, an activation action for the customer card may bedetected. As described above, the activation action may be tapping thecard to the mobile device. In another example, the action may be tappingthe card with the user's finger. When the activation action is detected,the customer card may be activated at block 908. The successfulactivation of the card may be communicated to the user by displaying anindication in AR, such as color coding, e.g., in green, the outline ofthe card.

The components and features of the devices described above may beimplemented using any combination of discrete circuitry, applicationspecific integrated circuits (ASICs), logic gates and/or single chiparchitectures. Further, the features of the devices may be implementedusing microcontrollers, programmable logic arrays and/or microprocessorsor any combination of the foregoing where suitably appropriate. It isnoted that hardware, firmware and/or software elements may becollectively or individually referred to herein as “logic” or “circuit.”

At least one computer-readable storage medium may include instructionsthat, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Moreover, unless otherwise noted the features described above arerecognized to be usable together in any combination. Thus, any featuresdiscussed separately may be employed in combination with each otherunless it is noted that the features are incompatible with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein, which form part of one or more embodiments.Rather, the operations are machine operations.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for therequired purpose and may be selectively activated or reconfigured by acomputer program stored in the computer. The procedures presented hereinare not inherently related to a particular computer or other apparatus.The required structure for a variety of these machines will appear fromthe description given.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thus,the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

What is claimed is:
 1. An apparatus comprising: a near-fieldcommunication (NFC) reader; one or more processors operable to executestored instructions that, when executed, cause the one or moreprocessors to: receive a uniform resource locator (URL) from acontactless card via the NFC reader, wherein the URL is associated witha download location for a software app; determine whether the softwareapp is already available; in response to the software app not beingavailable, download the software app from the download location providedby the URL and launch the software app; receive, via at least onecamera, a plurality of images of the contactless card; display inaugmented reality, via the software app, information adjacent to or onthe card based at least in part on the received plurality of images ofthe contactless card; detect an activation action; cause activation ofthe contactless card based on the detected activation action; anddisplay in AR, via the software app, notification of the activation ofthe contactless card.
 2. The apparatus of claim 1, wherein the one ormore processors are further caused to: automatically launch the softwareapp in response to the software app being already available on theapparatus.
 3. The apparatus of claim 1, wherein the one or moreprocessors are further caused to: identify at least a first component ofthe contactless card based at least in part on the received plurality ofimages of the contactless card, and wherein the information is: a firstinformation related to the first component of the contactless card, asecond information related to the contactless card, or a thirdinformation related to a user-selectable control for the contactlesscard.
 4. The apparatus of claim 3, wherein the one or more processorsare further caused to: identify a second component of the customer cardbased on the received plurality of images; and display in AR, via thesoftware app, fourth information related to the second component of thecustomer card adjacent to the first component based on the receivedplurality of images, and wherein the first component or the secondcomponent is a graphical indication, text, or a physical componentarranged on the customer card.
 5. The apparatus of claim 3, wherein thethird information related to the user selectable control comprises: (i)adding or removing one or more authorized users to the customer card or(ii) updating, changing, or setting up autopay for the customer card,and wherein the user selectable control allows a user associated withthe customer card to add or remove the one or more authorized users orallows the user to update, change, or set up the autopay.
 6. Theapparatus of claim 1, wherein the one or more processors are furthercaused to: upon the launching of the software app, (i) performregistration procedures of a user associated with the customer card ifthe user is a new user or (ii) perform login procedures of the user ifthe user is an existing user; and determine that the customer card is tobe activated.
 7. The apparatus of claim 6, wherein the URL is includedin the customer card, a sticker, or a QR code, and wherein the one ormore processors are further cause to receive the URL when customer cardis brought near or tapped to the apparatus, the sticker is brought near,read or scanned by the apparatus, or the QR code is brought near, reador scanned by the apparatus.
 8. A method comprising: receiving, via anear field communication (NFC) reader, a uniform resource locator (URL)from a contactless card via NFC, wherein the URL is associated with adownload location for a software app; determining, via one or moreprocessors, whether the software app is already available; in responseto the software app not being available, downloading the software appfrom the download location provided by the URL and launch the softwareapp; receiving, via at least one camera, a plurality of images of thecontactless card; displaying in augmented reality, via the software app,information adjacent to or on the card based at least in part on thereceived plurality of images of the contactless card; detecting anactivation action; causing, via the one or more processors, activationof the contactless card based on the detected activation action; anddisplaying in AR, via the software app, notification of the activationof the contactless card.
 9. The method of claim 8, further comprising:automatically launching the software app in response to the software appbeing already available on the apparatus.
 10. The method of claim 8,further comprising: identifying at least a first component of thecontactless card based at least in part on the received plurality ofimages of the contactless card, and wherein the information is: a firstinformation related to the first component of the contactless card, asecond information related to the contactless card, or a thirdinformation related to a user-selectable control for the contactlesscard.
 11. The method of claim 10, further comprising: identifying asecond component of the customer card based on the received plurality ofimages; and displaying in AR, via the software app, fourth informationrelated to the second component of the customer card adjacent to thefirst component based on the received plurality of images, and whereinthe first component or the second component is a graphical indication,text, or a physical component arranged on the customer card.
 12. Themethod of claim 10, wherein the third information related to the userselectable control comprises: (i) adding or removing one or moreauthorized users to the customer card or (ii) updating, changing, orsetting up autopay for the customer card, and wherein the userselectable control allows a user associated with the customer card toadd or remove the one or more authorized users or allows the user toupdate, change, or set up the autopay.
 13. The method of claim 8,further comprising: upon the launching of the software app, (i)performing registration procedures of a user associated with thecustomer card if the user is a new user or (ii) performing loginprocedures of the user if the user is an existing user; and determiningthat the customer card is to be activated.
 14. The method of claim 13,wherein the URL is included in the customer card, a sticker, or a QRcode, and wherein the one or more processors are further cause toreceive the URL when customer card is brought near or tapped to theapparatus, the sticker is brought near, read or scanned by theapparatus, or the QR code is brought near, read or scanned by theapparatus.
 15. A non-transitory computer-readable storage medium storingcomputer-readable program code executable by at least one processor to:receive a uniform resource locator (URL) from a contactless card via theNFC reader, wherein the URL is associated with a download location for asoftware app; determine whether the software app is already available;in response to the software app not being available, download thesoftware app from the download location provided by the URL and launchthe software app; receive, via at least one camera, a plurality ofimages of the contactless card; display in augmented reality, via thesoftware app, information adjacent to or on the card based at least inpart on the received plurality of images of the contactless card; detectan activation action; cause activation of the contactless card based onthe detected activation action; and display in AR, via the software app,notification of the activation of the contactless card.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein thecomputer-readable program code causes the at least one processor to:automatically launch the software app in response to the software appbeing already available on the apparatus.
 17. The non-transitorycomputer-readable storage medium of claim 15, wherein thecomputer-readable program code causes the at least one processor to:identify at least a first component of the contactless card based atleast in part on the received plurality of images of the contactlesscard, and wherein the information is: a first information related to thefirst component of the contactless card, a second information related tothe contactless card, or a third information related to auser-selectable control for the contactless card.
 18. The non-transitorycomputer-readable storage medium of claim 17, wherein the thirdinformation related to the user selectable control comprises: (i) addingor removing one or more authorized users to the customer card or (ii)updating, changing, or setting up autopay for the customer card, andwherein the user selectable control allows a user associated with thecustomer card to add or remove the one or more authorized users orallows the user to update, change, or set up the autopay.
 19. Thenon-transitory computer-readable storage medium of claim 15, wherein thecomputer-readable program code causes the at least one processor to:upon the launching of the software app, (i) perform registrationprocedures of a user associated with the customer card if the user is anew user or (ii) perform login procedures of the user if the user is anexisting user; and determine that the customer card is to be activated.20. The non-transitory computer-readable storage medium of claim 18,wherein the URL is included in the customer card, a sticker, or a QRcode, and wherein the one or more processors are further cause toreceive the URL when customer card is brought near or tapped to theapparatus, the sticker is brought near, read or scanned by theapparatus, or the QR code is brought near, read or scanned by theapparatus.